Method and system for file-system based caching

ABSTRACT

A method and system for file-system based caching can be used to improve efficiency and security at network sites. In one set of embodiments, the delivery of content and storing content component(s) formed during generation of the content may be performed by different software components. Content that changes at a relatively high frequency or is likely to be regenerated between requests may not have some or all of its corresponding files cached. Additionally, extra white space may be removed before storing to reduce the file size. File mapping may be performed to ensure that a directory within the cache will have an optimal number of files. Security at the network site may be increased by using an internally generated filename that is not used or seen by the client computer. Many variations may be used is achieving any one or more of the advantages described herein.

RELATED APPLICATIONS

This application is a continuation of, and claims a benefit of priorityunder 35 U.S.C. 120 of the filing date of U.S. patent application Ser.No. 11/348,645, filed Feb. 7, 2006, now allowed, entitled “METHOD ANDSYSTEM FOR FILE-SYSTEM BASED CACHING”, which is a continuation of U.S.patent application Ser. No. 10/195,798, filed Jul. 15, 2002, now U.S.Pat. No. 7,024,452, entitled “METHOD AND SYSTEM FOR FILE-SYSTEM BASEDCACHING,” which claims priority from Provisional Application No.60/305,320, filed Jul. 13, 2001, entitled “METHOD AND SYSTEM FORFILE-SYSTEM BASED CACHING.” This application also relates to U.S. patentapplication Ser. No. 11/641,496, filed Dec. 18, 2006, now allowed, whichis a continuation-in-part of U.S. patent application Ser. No.11/348,645, filed Feb. 7, 2006, and which is a continuation of U.S.patent application Ser. No. 10/334,515, filed Dec. 31, 2002, now U.S.Pat. No. 7,349,942, entitled “STORAGE MEDIUM HAVING A MANAGEABLE FILEDIRECTORY STRUCTURE,” which claims priority from Provisional ApplicationNo. 60/356,613, filed Feb. 13, 2002, entitled “CACHE MEMORY HAVING AHIERARCHICAL STRUCTURE.” The entire contents of all the above referencedapplications are hereby expressly incorporated by reference for allpurposes.

TECHNICAL FIELD OF THE INVENTION

This invention relates generally to a method of processing content at anetwork site, and more particularly, to a method of delivering andstoring content at a network site, a system, and a data processingsystem readable medium for carrying out the method.

DESCRIPTION OF THE RELATED ART

The Internet includes a large collection of computers operated under aclient-server computer network model. FIG. 1 includes an exemplaryhardware configuration for accessing a site on a network. A clientcomputer 12 is bi-directionally coupled to a network 14, such as theInternet. A web server 16 is bi-directionally coupled to the network 14,a page generator 18, and a cache 19. Cache 19 may be part of the webserver 16 or as a separate hard disk. Specific methods of using thenetwork are described in more detail below.

Many different types of protocols can support dynamic generation ofcustomized pages. U.S. Pat. No. 5,740,430 (“Rosenberg”) and U.S. patentapplication Ser. No. 09/965,914, entitled “Method and System for CacheManagement of Dynamically-Generated Content,” filed on Sep. 28, 2001(the “Cache Management Application”) disclose methods and systems forcaching custom pages to reduce page regeneration. In one conventionalmethod, a request for content in the form of a Uniform Resource Location(“URL”) can be sent from the client computer 12 to the web server 16using the network 14. The web server 16 can convert the URL to acustomized URL or “CURL.” The web server 16 uses the CURL to determineif the content is in the cache 19. If the content is in the cache 19 (a“cache hit”), the web server 16 retrieves the content from the cache 19and sends it to the client computer 12.

If the web server 16 did not find the content within the cache 19 (a“cache miss”), the web server 16 instructs the page generator 18 togenerate the content. After generating the content, the page generator18 sends the content to the web server 16. The web server computer 16stores the content to the cache 19 in accordance with the CURL. After orduring storing, the content is sent from the web server 16 to the clientcomputer 12 via the network 14.

The conventional method suffers from problems related to the design anddistribution of operations between the hardware and software componentsat the network site. The process of storing a file is a time consumingprocess. If the web server 16 stores content before sending it to theclient computer 12, the user of the client computer 12 waits for thestore to complete. Other users at different client computers (not shown)may also be affected because more of the web server's processing time isoccupied by the storing operation. Therefore, all users sending requeststo the web server 16 can also be impacted by any cache miss regardlesswhether they caused the cache miss.

Another problem with the conventional method is related to how files arestored in the cache 19. The cache 19 may have potentially millions offiles within a single discrete directory. The time needed to search thecache can be significantly longer when the number of files within adiscrete directory becomes larger, especially when over a million filesare within one directory. Therefore, even if a cache hit occurs,valuable processing time on the web server 16 is occupied searching thecache 19. Again, all users at client computers making requests to theweb server 16 can be adversely impacted.

Still another problem is related to storing. More specifically, allcontent generated by the page generator 18 is saved within the cache 19.Therefore, regardless whether the content or any portion of it is staticor dynamic, all content sent to the web server 16 from the pagegenerator 18 is stored in the cache 19. If the content or any portion ofit constantly changes, blindly caching the content can effectively be awaste of valuable computer resources.

The conventional methods also cause a security concern. The web server16 can store content within the cache 19. In other words, theconventional system can allow a user request to a network site toinitiate a store operation to cache 19 using the network site's servercomputer(s). Network site operators, and particularly their securitypersonnel, are concerned with any publicly-initiated store operationsusing their server computers because such processes can be manipulatedand can lead to potential security breaches.

SUMMARY

A method and system for file-system based caching can be used to improveefficiency and security at network sites. In one set of embodiments, thedelivery of content and storing content component(s) formed duringgeneration of the content may be performed by different softwarecomponents. Content that changes at a relatively high frequency or islikely to be regenerated between requests may not have some or all ofits corresponding files cached. Content components may be cachedindependently from content, so that multiple copies of a singlecomponent are not cached with every network page using that component.Also, different content component(s) of the same network page may bestored within different directories. Additionally, extra white space maybe removed before storing to reduce the file size. File mapping may beperformed to ensure that a directory within the cache will have no morethan approximately 4100 files. Security at the network site may beincreased by using an internally generated filename that is not used orseen by the client computer. Many variations may be used in achievingany one or more of the advantages described herein. None of theadvantages, by itself or collectively, should be construed as anessential or critical to the present invention.

In one set of embodiments, a computer program can comprise code embodiedin a data processing system readable medium. The code can comprise aninstruction for sending requested content to a client computer. Theinstruction for sending can be performed using a first softwarecomponent. The code can comprise an instruction for storing a contentcomponent that forms at least part of the requested content. Theinstruction for storing can be performed using a second softwarecomponent. The sending of content may be performed by a web server orpage generator software component, and the storing may be performed bythe page generator or a cache manager software component, however, thesame software component should not be used for sending and storing.

In another set of embodiments, the code can comprise an instruction forforming an instruction for generating content in response to a request.The content may comprise a content component. The code can also comprisean instruction for determining whether the content component is or isnot to be stored within a cache.

In still another set of embodiments, the code can comprise aninstruction for parsing a request for requested content to form a parsedelement corresponding to a caching-related parameter. The code can alsocomprise an instruction for performing an operation in response to avalue of the parsed element.

In other embodiments, methods and systems can be used to perform actionsin accordance with the instructions corresponding to the code of thedata processing system readable medium. Additional actions may beperformed by humans in conjunction with their associated computers. Thecomputer program may reside on one or more computers.

The foregoing general description and the following detailed descriptionare exemplary and explanatory only and are not restrictive of theinvention, as defined in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the accompanying figures.

FIG. 1 includes an illustration of a hardware configuration for anetwork site.

FIG. 2 includes an illustration of a hardware configuration for anetwork site in accordance with an embodiment of the present invention.

FIG. 3 includes an illustration of a data processing system storagemedium including software code having instructions in accordance with anembodiment of the present invention.

FIGS. 4-6 include a process flow diagram for using the hardwareconfiguration of FIG. 2.

Skilled artisans appreciate that elements in the figures are illustratedfor simplicity and clarity and have not necessarily been drawn to scale.For example, the dimensions of some of the elements in the figures maybe exaggerated relative to other elements to help to improveunderstanding of embodiments of the present invention.

DETAILED DESCRIPTION

Reference is now made in detail to the exemplary embodiments of theinvention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts (elements).

A method and system for file-system based caching can be used to replymore quickly to client computer requests, cache more quickly andefficiency for only those content component(s) that should be cached,reduce the file size of files cached, optimize the number of fileswithin directories, improve security at network sites, and potentiallyfor other reasons. In one set of embodiments, the delivery of contentand storing file(s) used in generating the content may be performed bydifferent software components that are on the same server computer ordifferent server computers. Content that changes at a relatively highfrequency or is likely to be regenerated between requests may not havesome or all of its corresponding files cached. Also, different contentcomponent(s) of the same network page may be stored within differentdirectories. Additionally, extra white space may be removed beforestoring to reduce the file size. File mapping may be performed to ensurethat a directory within the cache will have an optimal number of files.Security at the network site may be increased by using an internallygenerated filename is not used or seen by the client computer. Manyvariations may be used in achieving any one or more of the advantagesdescribed herein. None of the advantages, by itself or collectively,should be construed as an essential or critical to the presentinvention.

Before discussing embodiments of the present invention, a hardwarearchitecture for using embodiments is described. FIG. 2 illustrates anexemplary architecture and includes a client computer 12 that can bebi-directionally coupled to a network 14, and a web server 26 that isbi-directionally coupled to the network 14, page generator 28, the cachemanager 28, and a cache 29. The cache manager 24 can be bi-directionallycoupled to the page generator 28 and the cache 29. Many otheralternative configurations are possible and known to skilled artisans.For example, the cache manager 24 is not required, and the computers 26and 28 may be bi-directionally coupled to the cache 29. Also, the cachemanager may be coupled to the web server 26 to send filenames of filesthat are stored within the cache 29 (i.e., unidirectional couplingrather than bi-directional coupling).

The client computer 12 includes a central processing unit (“CPU”) 120, aread-only memory (“ROM”) 122, a random access memory (“RAM”) 124, a harddrive (“HD”) or storage memory 126, and input/output device(s) (“I/O”)128. The I/O devices 128 can include a keyboard, monitor, printer,electronic pointing device (e.g., mouse, trackball, etc.), or the like.The client computer 12 can include a desktop computer, a laptopcomputer, a personal digital assistant, a cellular phone, or nearly anyother device capable of communicating over the Internet or an intranet.

The web server 26 can include a CPU 260, ROM 262, RAM 264, HD 266, I/O268, and a plug-in 269. The page generator 28 can include a CPU 280, ROM282, RAM 284, HD 286, I/O 288, and a servlet (engine) 289. In onenon-limiting embodiment, the page generator can be used to fulfillrequests of coming from the web server 26. The cache manager 24 caninclude a CPU 240, ROM 242, RAM 244, HD 246, and I/O 248. Each of thecomputers in FIG. 2 may have more than one CPU, ROM, RAM, HD, I/O, orother hardware components. For simplicity, each computer is illustratedas having one of each of the hardware components, even if more than oneis actually used.

Details of the web server plug-in 269 and the servlet 289, which can besoftware modules, are described below in more detail. Although theplug-in 269 and servlet 289 are typically stored in HD 266 and HD 286,respectively, and loaded into RAM 264 and RAM 284, respectively, whenused. The plug-in 269 and servlet 289 are illustrated as separatecomponents to simplify understanding of the present invention.

Each of the computers 12, 24, 26, and 28 is an example of a dataprocessing system. ROM 122, 242, 262, and 282; RAM 124, 244, 264, and284; HD 126, 246, 266, and 286; and the cache 29 include media that canbe read by the CPU 120, 240, 260, or 280. Therefore, each of these typesof memories includes a data processing system readable medium. Thesememories may be internal or external to the computers 12, 24, 26, and28.

The methods described herein may be implemented in suitable softwarecode that may reside within ROM 122, 242, 262, or 282, RAM 124, 244,264, or 284, or HD 126, 246, 266, or 286. In addition to those types ofmemories, the instructions in an embodiment of the present invention maybe contained on a data storage device with a different data processingsystem readable storage medium, such as a floppy diskette. FIG. 3illustrates a combination of software code elements 304, 306, and 308that are embodied within a data processing system readable medium 302,on HD 266. Alternatively, the instructions may be stored as softwarecode elements on a DASD array, magnetic tape, floppy diskette, opticalstorage device, or other appropriate data processing system readablemedium or storage device.

In an illustrative embodiment of the invention, the computer-executableinstructions may be lines of compiled C⁺⁺, Java, or other language code.Other architectures may be used. For example, the functions of any oneof the computers may be performed by a different computer shown in FIG.2. Additionally, a computer program or its software components with suchcode may be embodied in more than one data processing system readablemedia in more than one computer. Further, other client computers (notshown) or other server computers (not shown) similar to client computer12 and server computers 24, 26 and 28, respectively, may also beconnected to the network 14. FIGS. 4-6 include illustrations, in theform of a flowchart, of the structures and operations of such softwareprograms.

In the hardware configuration above, the various software components(e.g., web server, page generator, cache manager, or the like) are onseparate server computers. In alternative embodiments, some or all ofthe software components may reside on the same server computer. Forexample, the web server software component and the page generatorsoftware component could reside on the same server computer. Forsimplicity, each of the software components in the embodiments belowresides on different server computers.

Communications between any of the computers in FIG. 2 can beaccomplished using electronic, optical, radio-frequency, or othersignals. When a user is at the client computer 12, the client computer12 may convert the signals to a human understandable form when sending acommunication to the user and may convert input from a human toappropriate electronic, optical, radio-frequency, or other signals to beused by the client computer 12 or the server computer 24, 26, or 28.Similarly, when an operator is at a server computer 24, 26, or 28, thatserver computer may convert the signals to a human understandable formwhen sending a communication to the user and may convert input from ahuman to appropriate electronic, optical, radio-frequency, or othersignals to be used by a server computer 24, 26, or 28 or the clientcomputer 12.

A few terms are defined or clarified to aid in understanding thedescriptions that follow. A network includes an interconnected set ofserver and client computers over a publicly available medium (e.g., theInternet) or over an internal (company-owned) system, A user at a clientcomputer may gain access to the network using a network access provider.An Internet Service Provider (“ISP”) is a common type of network accessprovider. A network address includes information that can be used by aserver computer to locate information, whether internal to that servercomputer or at a different, remote computer or database. UniformResource Locators (“URLs”) are examples of network addresses. A networksite typically includes network pages or other information displays atdifferent network addresses for that network site. A web site is acommon type of network site, and a web page is a common type of networkpage. Note that the examples given within this paragraph are forpurposes of illustration and not limitation.

The term “content” is intended to mean information sent from a networksite to a client computer in response to a request from a user at theclient computer. The content is typically in the form of a network page.

The term “content component” is intended to mean at least a portion ofthe content. In many instances, the content can include a plurality ofcontent components. However, in some instances, the content can be asingle content component.

Content, a content component, or both may include a static or dynamicfile. A static file does not typically change with time. A dynamic filetypically changes with time. Dynamic files may change at a relativelylow frequency (e.g., daily, weekly, monthly, annually, etc.) or at arelatively high frequency (e.g., hourly or more frequently, differentcontent each time it is requested, etc.).

The term “network site” is intended to comprise computers used duringthe normal operation of the network site in response to a request from aclient computer. The client computer 12 is outside the network site butmay request content from the network site via communications with webserver 26.

The term “software component” is intended to mean at least a portion ofa computer program (i.e., a software application). Examples include aweb server software component, a page generator software component, acache manager, and the like. Different software components may reside inthe same computer program or in different computer programs on the samecomputer or different computers.

The term “white space” is intended to mean occurrences of informationwithin source code that is ignored by computer if the source code wereto be compiled or interpreted by a computer. For example, if one space,two spaces, or one hundred spaces lie between characters, a computer cantreat any of these as a single space or no space between characters.Other white space may include tabs and new line commands.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a method,process, article, or apparatus that comprises a list of elements is notnecessarily limited only those elements but may include other elementsnot expressly listed or inherent to such method, process, article, orapparatus. Further, unless expressly stated to the contrary, “or” refersto an inclusive or and not to an exclusive or. For example, a conditionA or B is satisfied by any one of the following: A is true (or present)and B is false (or not present), A is false (or not present) and B istrue (or present), and both A and B are true (or present).

FIGS. 4-6 include a process flow diagram of a method of processingcontent at the network site illustrated in FIG. 2. The method will bebriefly addressed before details of the method are described. The methodcan comprise receiving a client request from a client computer 12 asshown in block 402 of FIG. 4. The method can further comprise applyingan algorithm to the client request to parse the client request and formparsed elements (block 422) and generating a mapped filename from atleast one of the parsed elements (block 424). A determination can thenbe made whether the file(s) for the content component(s) is (are) in thecache 29 (diamond 426). If the content is in the cache 29, the methodcan further comprise retrieving the file(s) and sending requestedcontent to the client computer 12 (block 428). Otherwise (“No” branch ofdiamond 426), a cache miss has occurred.

When a cache miss has occurred, the method can comprise generating thecontent or any of its content component(s) at the page generator 28 asshown in block 502 of FIG. 5. The method can also comprise trackingcontent component(s) and instruction(s) used in generating those contentcomponent(s) (collectively, “tracking information”) (block 522). Aftercapturing the tracking information, the method can further comprisesending the generated content from the page generator 28 to the webserver 26 (block 542). The method can still further comprise addingcontent to or modifying the generated content consistent with a webserver inclusion (block 562) and sending the requested content to theclient computer 12 (block 564).

Any time after the generated content is generated (“B” reference in FIG.5), the method can still further comprise forwarding the contentcomponent(s) and tracking information from the page generator 28 to thecache manager 24 as shown in block 602 of FIG. 6. A determination can bemade as to which content components, if any, should be cached (diamond622). The method can also comprise preprocessing the contentcomponent(s) before storing (block 624). The method can yet furthercomprise caching content component(s) into the cache 29 and updating thefile registry at the web server 26 (block 626).

After reading this specification, skilled artisans will appreciate thatsome of the activities described in FIGS. 4-6 may not be required butmay provide a more efficiently running network. Also, some of theoperations may be moved from one network site computer to anothernetwork site computer in order to return requested content to clientcomputers faster. Attention is now turned to a more detailed descriptionof the method illustrated in FIGS. 4-6 and its variants.

Before beginning the method illustrated in FIGS. 4-6, an operator at thenetwork site may develop a mapping algorithm. The mapping algorithm cantake the URL and other information with the user request (e.g., locale,language, browser, operating system, etc.), collectively “clientrequest,” and parse the client request into parsed elements that maycorrespond to different parameters. The software components,particularly the web server 26 and the page generator 28, may analyzethe parsed elements in determining what content should be sent to theclient computer 12. Some of the parameters can be used for web serverside inclusion(s). More information about the web server side inclusionsis described later in this specification. Another parameter can includea user identifier, query string, a markup language for the clientcomputer (e.g., HTML, WML, etc.), operating system of the clientcomputer 12, a locale or language associated with the client computer12, or the like. The parsing is highly flexible and can be adapteddifferently to different network sites.

Returning to block 402 in FIG. 4, a user at client computer 12 can sendand the web server 28 can receive a client request including a URL. Asan example of the URL portion of the client request can be“http://www.homedepot.com/diy_main/pg_diy.jsp?CNTKEY=growit”. The methodcan further comprise applying the mapping algorithm (previouslydescribed) to the client request to parse the client request to formparsed elements that correspond to different parameters. At least one ofthe parsed elements may correspond to a caching-related parameter thatcan be used to determine when a content component is to be regeneratedor its context. The context may includes information that can allow acache manager to later reconstruct an original client request forcontent that includes the content component in order to performregeneration and caching of the content component.

The method can comprise generating a mapped filename from at least oneof the parsed elements (block 424). One format can comprise a namingconvention that uses concatenation of the parsed elements with commas toseparate the fields. For example, “0,CNTKEY=growit,00-EN_US.html” may beused. A software component, such as the web server 26 or the pagegenerator 28, may analyze the parsed elements to determine what contentis needed for the client request.

Optionally, the method can comprise generating a mapped filename from atleast one of the parsed elements (block 424) by applying a hashingfunction over the parameters in those parsed elements. For example, allthe parsed elements may be used in the hashing function. The hashingfunction may help to control filename explosion within a discretedirectory and help keep the number of files in a directory closer to anoptimal level for the specific hardware and software configuration usedat the network site. For example, the filename might become“EN_US/hash00345/CNTKEY=growit.html”.

By using a hashing function to cache files into separately nameddiscrete directories, the method can manage the size of the directory inwhich a file is cached to a number of files that keeps access andupdating operations at an efficient level. In one non-limitingembodiment, the number of files within a discrete directory can be at alevel such that file-searching operations can be performed close to thespeed of the storage system (e.g., a hard disk). The manageable numbermay depend on hardware or other limitations of the system. For example,in one system, when the number of files per directory is greater thanapproximately 4100 files, file operations may begin to take longer thanthe hardware limitations of a hard disk. The filename mapping can createa filename that allows efficient reproduction of a request for cacheregeneration.

The mapping algorithm needs to be known by the software components inthe network site for accessing, generating, and storing cached content,but a particular algorithm, such as using a hashing function, is notrequired to achieve the caching capabilities described herein. Nearlyany mapping algorithm can be used. Concatenation and hashing have beendescribed. After reading this specification, skilled artisans willappreciate that many other algorithms can be used. The mapping algorithmproduces the mapped filename that may correspond to the client requestbut uses an internal format understood by software components within thenetwork site. The plug-in 269 can be used to perform the parsing andmapping functions.

After the filename has been identified in accordance with the algorithm,the method can further include determining whether the file(s) is (are)in the cache 29 (diamond 426). This determination can be performed usinga conventional method. In one embodiment, after generating the mappedfilename, the web server 26 can refer to a file registry within the webserver 26 to determine if the mapped filename corresponds to (i.e.,matches) a file within the cache 29. If at least one file matches thefilename, the method can comprise retrieving the file(s) and sending it(them) to the client computer 12 (block 428). At this point, the methodmay end.

In still another embodiment, the file(s) may be cached in a memory-onlycache with no disk for persistence (e.g., in a volatile memory). Thehash can define how to find the file(s) without regard to the directorystructure within the cache.

In another alternative embodiment, the web server 26 can perform a webserver side inclusion. If some, but not all, of the content component(s)are in the cache 29, the web server 26 may retrieve the file(s) forthose content component(s) from the cache 29 and send an instruction tothe page generator 28 to generate the missing content component(s).After generation, those remaining content component(s) are sent to theweb server 26 where they can be included with the retrieved file(s).

After the web server 26 has all the retrieved or generated contentcomponents, the web server 26 can add to or modify information from thefile(s) before sending the content to the client computer 12. Forexample, if the client computer 12 is a cell phone that is designed towork in WML and the content received by the web server 26 is in HTML,the web server 26 can convert the content in HTML to WML. Alternatively,the display for client computer 12 may vary from device to device. Forexample, if the client computer 12 is a cell phone, the web side serverinclusion can reformat the information to be more user friendly for acell phone. Note that the internal (mapped) filename may or may not besent or otherwise be available to the client computer 12. Therefore, theclient computer 12 does not know the true filename at the network sitesince the internal mapped filename may include the hashed value neededto locate it within the back-end systems of the network site (e.g.,cache 29).

If any file corresponding to the content is not within the cache (“No”branch of diamond 426), the method can further comprise generating thecontent or any of its content component(s) at the page generator asshown in block 502 in FIG. 5. The page generator 28 can generate thenetwork page or any of its content components that were not in cache 29.

During content generation, the method can also comprise tracking contentcomponent(s) and instruction(s) used in generating those contentcomponent(s) (block 522). Assume that a fresh page is being created forthe first time and requires a content component to be created, and thecontent component is to be cached separately. During page generation ofthe overall page, APIs should be configured such that they can cause thecontent component to be generated as well to track or capture the startand end of the generated content component in the overall page so thatthe parameters for it are understood as well as the position and extentof the content component. Other tracking information generated by theAPIs may correspond to web server side inclusions, which have previouslybeen described. This information might be embedded in markers in theoverall page or stored separately from the overall page. This trackinginformation can be captured by the page generator 28 and then used bythe cache manager 24 to store the overall page and its embedded contentcomponent as two separately cached pages with a reference to the contentcomponent left in the overall page. In this manner, the contentcomponent can be referenced by other pages but stored only once.

Examples of content components that may not be cached can includecontent that changes at a relatively high frequency (e.g., dynamic fileswith content that changes on an hourly basis or more frequently), suchas news headlines or content that is infrequently requested (e.g., thefile may be flushed from the cache before a subsequent request for thesame file would occur). For example, prior purchases by the user at anetwork site may not be cached. In one non-limiting embodiment, theservlet 289 may be a J2EE-compliant servlet engine for Java Server Pages(“JSP”). Other types of page generators may be used.

After the content has been generated by the page generator 28, themethod can continue with sending the generated content from the pagegenerator 29 to the web server 28 (block 542). The method can furthercomprise adding content to or modifying the generated content consistentwith web server side inclusion(s) (block 562). The adding ormodification using the web server side inclusion as previouslydescribed. Alternatively, the addition or modification may be a changein a markup language (HTML to WML), reformatting the content for theparticular display of the client computer 12 (e.g., cell phone, personaldigital assistant, pager, laptop computer, etc.), including the localtime of the client computer, or potentially other additions ormodifications.

After the web server side inclusions, if any, the method can comprisesending the requested content to the client computer 12 (block 564).Note that the activities used in storing any or all the generatedcontent to the cache may not be completed or even started before therequested content is sent to the client computer 12. Therefore, theclient computer 12 should receive the requested content quicker comparedto conventional methods.

In an alternative embodiment, the method can include removing or hidingthe internally formatted filename from external viewing at the clientcomputer 12. This can be accomplished using simple references (e.g.,numeric references) to a managed table that contains the data. Themanaged table (along with the indices from the API tracking information)can allow an indirect agent (e.g., cache manager 24) to subsequentlystore the cached version of generated content to memory (e.g., todatabase 19) while keeping the source reference hidden from therequesting client computer 12.

Referring to reference “B” in FIGS. 5 and 6, the method can furthercomprise forwarding the generated content and tracking information(generated by the APIs) from the page generator 29 to the cache manager24 as seen in block 602 in FIG. 6. The generated content can comprisemetadata about where to cache the content component(s) if it is (theyare) to be cached. The metadata can include opt-in or opt-outparameters, such as whether or not to cache any specific contentcomponent, and potentially other parameters, so that effective cachedfile names (at least partially human understandable names) can be used.Other metadata about the cached file may include information regardingwhen or how often content for the content components will be updated,revised, or the like. For example, the metadata can include Time To Live(TTL) information, so that automated updates to the content component(s)can occur. This other metadata may be separately provided to the cachemanager 24 by a configuration file, as a message to the cache manager24, or the like.

A determination can be made whether file(s) for the generated content is(are) to be cached (diamond 622). If none of the generated content is tobe cached (“No” branch of diamond 622), the process can end.

Otherwise (“Yes branch of diamond 622), the method can includepreprocessing the content component(s) before storing them. Examplesinclude removing any or all of the white space within the source code ofthe content component, encrypting the content component, countinginstances of a particular character, set of characters, object or thelike, and nearly any other information that an operator of the networksite may desire.

The method can include caching content component(s) at location(s)corresponding to the mapped filename(s) and updating the file registryfor the web server 26 (block 626). Note that caching a content componentshould be construed to include adding or updating an entry within adatabase.

The cache manager 24 can use a temporary file during the mapping andstoring portions of the caching operation. As the generated content isreceived by the cache manager 24 and placed into a temporary file, theAPI markers or other metadata corresponding to an aspect of caching(e.g., whether a content component is or is not to be cached, timingregarding updates of cached material, or the like) are examined.

The cache manager 24 can produce TTL timers on its own or thatcorrespond to one of the parsed elements (caching-related parameter)from the client request so that updates can occur on a set schedule,which can be arbitrarily determined for a given application. Thefile-based caching method can thus provide savings in system performancewith regards to the cached file production, can fit naturally into anetwork site environment, and can provide for a more secure site (thecache manager 24 can “live” behind a network site's firewall (not shownin FIG. 2), such that no processes outside of the firewall can initiatea write to cache 29).

Alternatively, or in conjunction with the TTL timers, the cache manager24 can also use a caching-related parameter from the parsed elements todetermine which network pages need to be regenerated when a specificcontent component is regenerated (sometimes because the priorinformation is stale or incorrect).

During mapping, the cache manager 24 can refer to the API trackinginformation before caching the content component(s), but can stillmaintain an association between the cached file and the trackinginformation by virtue of mapping. The mapped filename(s) can be thefinal cache destination(s) of the file(s) that is (are) to be cached.The cache manager 24 can store the file(s) within the cache 29 and thendelete the temporary file. Note that the generation of a temporary fileor the storing of the content component is not performed by the webserver 26. After mapping and caching are completed, information from thecache manager 24 can be sent to the web server 26 to update the fileregistry, so that the web server 26 can directly access the cache 29 forthe next request for the same or similar content.

In another embodiment, the mapped filename can be generated andtemporarily block for a different request for the same content ordifferent content using a common content component that is currentlybeing generated. The blocking may last until the cache placement(storing to cache 29) is completed so that subsequent requests areblocked until the content component is cached. In another embodiment,the blocking may be shorter. For example, the blocking can terminateafter the content component is generated if the page generator 28 hasaccess to the mapped filenames or the ability to generate them. In thismanner, duplicate requests for the same content component(s) contentcomponent being generated or just have may be substantially preventedduring the time it takes to produce a cached content component.

In still another embodiment, the page generator 28 may also act as theweb server 26 and may fulfill requests from the client computerdirectly. In yet another embodiment, the page generator 28 may also actas the cache manager 24. However, the same software component should notdeliver content to the client computer and store content component(s).

An advantage in some embodiments may include the faster delivery time ofcontent to the client computer 12. Note that the caching of the file(s)corresponding to the generated content can occur asynchronously withrespect to the operations at the web server 26. If the cost of producinga cached page in a conventional system (e.g., FIG. 1) isC_(request)+C_(generation)+C_(placement) (where C=cost), the networksite configuration in FIG. 2 can eliminate the placement costs by usingthe servlet 289 to cause at least a portion of the content componentbeing generated to be stored asynchronously. Therefore, the requestedcontent can be provided to client computer 12 without the performancehit caused by storing or caching any or all of the content since thestoring or caching operation is not performed by the web server 26.

Still another advantage in one embodiment can include the ability toselectively cache or not cache file(s) (content component(s)) for agenerated network page. A network site designer or operator maydetermine what is or is not to be cached by the cache manager 24. Anyfile used within the generated content that is dynamic and changes at arelatively high frequency (e.g., new data for every time it isgenerated) or is likely to be regenerated between requests should not becached. Caching those file(s) can represent wasted space within thecache and the file directory used with the cache. This aspect of thenetwork site is transparent to the user at client computer 12 exceptthat he or she gets requested content back quicker.

A further advantage can include independently caching content componentsfrom network pages. Some of the content components (i.e., files) may beused in other network pages. Storing multiple copies of the sameinformation occupies additional memory space and slows retrieval of thisor other content component(s) since the number of stored files may begreater. Therefore, the number of copies of the content component willbe less than the number of network pages in which the content componentis used, and may be as little as one copy of the component. Also,content component(s) may be stored at locations independent of othercontent component(s) within the same network page. This can allow bettercontrol over the number of files within each discrete directory andspeed the read access time for the content component. Additionally,quicker retrieval can translate to quicker delivery of already cachedcontent.

Another advantage in one embodiment may include removing excess whitespace. Excess white space removal can be an optimization for the cachedfile because it reduces the number of bytes delivered over the network(e.g., the Internet). By eliminating the white space, the size(s) offile(s) may be 30% smaller within the cache 29. Note that in anon-limiting embodiment, the removal of the white space from a contentcomponent is permanent. Simply put, this removal is not conventionalfile compression. Such a savings can be realized in faster writing andreading times for files.

In the foregoing specification, the invention has been described withreference to specific embodiments. However, one of ordinary skill in theart appreciates that various modifications and changes can be madewithout departing from the scope of the present invention as set forthin the claims below. Accordingly, the specification and figures are tobe regarded in an illustrative rather than a restrictive sense, and allsuch modifications are intended to be included within the scope ofpresent invention.

Benefits, other advantages, and solutions to problems have beendescribed above with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any element(s) that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeature or element of any or all the claims.

1. A method for file-system based caching, comprising: preprocessing oneor more content components generated by a page generator, wherein acache manager performs the preprocessing; caching the one or morecontent components at one or more locations corresponding to one or moremapped filenames, wherein each of the one or more mapped filenames isgenerated from elements parsed from a client request for contentreceived at a web server and wherein the cache manager performs thecaching; and updating a file registry for the web server.
 2. The methodaccording to claim 1, wherein the preprocessing comprises removing anyor all white spaces within source code of a content component.
 3. Themethod according to claim 1, wherein the preprocessing comprisesencrypting a content component.
 4. The method according to claim 1,wherein the preprocessing comprises counting instances of a particularcharacter, a set of characters, an object, or other designatedinformation.
 5. The method according to claim 1, wherein the cachingcomprises adding or updating an entry within a database.
 6. The methodaccording to claim 1, further comprising: as the one or more contentcomponents are received by the cache manager and placed into a temporaryfile, examining application programming interface (API) markers ormetadata corresponding to an aspect of caching.
 7. The method accordingto claim 6, further comprising: determining whether a content componentis or is not to be cached.
 8. The method according to claim 1, furthercomprising: producing at least one time to live (TTL) timercorresponding to one of the elements parsed from the client request forcontent, wherein the cache manager performs the producing.
 9. The methodaccording to claim 1, further comprising: using a parameter from one ofthe elements parsed from the client request for content to determinewhich network pages need to be regenerated when a specific contentcomponent is regenerated.
 10. A computer program product comprising atleast one non-transitory computer readable medium storing instructionstranslatable by at least one processor to perform: preprocessing one ormore content components generated by a page generator; caching the oneor more content components at one or more locations corresponding to oneor more mapped filenames, wherein each of the one or more mappedfilenames is generated from elements parsed from a client request forcontent received at a web server; and updating a file registry for theweb server.
 11. The computer program product of claim 10, wherein theinstructions are further translatable by the at least one processor toperform: removing any or all white spaces within source code of acontent component.
 12. The computer program product of claim 10, whereinthe instructions are further translatable by the at least one processorto perform: encrypting a content component.
 13. The computer programproduct of claim 10, wherein the instructions are further translatableby the at least one processor to perform: counting instances of aparticular character, a set of characters, an object, or otherdesignated information.
 14. The computer program product of claim 10,wherein the instructions are further translatable by the at least oneprocessor to perform: examining application programming interface (API)markers or metadata corresponding to an aspect of caching; anddetermining whether a content component is or is not to be cached. 15.The computer program product of claim 10, wherein the instructions arefurther translatable by the at least one processor to perform: producingat least one time to live (TTL) timer corresponding to one of theelements parsed from the client request for content.
 16. The computerprogram product of claim 10, wherein the instructions are furthertranslatable by the at least one processor to perform: using a parameterfrom one of the elements parsed from the client request for content todetermine which network pages need to be regenerated when a specificcontent component is regenerated.
 17. A system for file-system basedcaching, comprising: a web server communicatively coupled to a clientcomputer, wherein the web server is operable to receive a client requestfor content from the client computer; a page generator coupled to theweb server, wherein the page generator is operable to generate one ormore content components; and a cache manager coupled to the web server,wherein the cache manager is operable to: preprocess the one or morecontent components generated by the page generator; cache the one ormore content components at one or more locations corresponding to one ormore mapped filenames, wherein each of the one or more mapped filenamesis generated from elements parsed from the client request for contentreceived at the web server; and update a file registry for the webserver.
 18. The system of claim 17, wherein the cache manager is furtheroperable to: as the one or more content components are received andplaced into a temporary file, examine application programming interface(API) markers or metadata corresponding to an aspect of caching; anddetermine whether a content component is or is not to be cached.
 19. Thesystem of claim 17, wherein the cache manager is further operable to:produce at least one time to live (TTL) timer corresponding to one ofthe elements parsed from the client request for content.
 20. The systemof claim 17, wherein the cache manager is further operable to: use aparameter from one of the elements parsed from the client request forcontent to determine which network pages need to be regenerated when aspecific content component is regenerated.